bpo-46475: Add typing.Never and typing.assert_never#30842
Merged
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
10 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Another pending proposal from typing-sig.
Neverprimitive that is semantically identical toNoReturn, but documented explicitly as a bottom type. I chose to make it a separate object instead of a pure alias forNoReturnso that dynamic checkers can distinguish between the two and so that we can document them separately.assert_never()function to statically assert that code is unreachable. Based on @davidfstr's feedback, the error raised by the function does not include the argument.https://bugs.python.org/issue46475